約 4,399,184 件
https://w.atwiki.jp/m_shige1979/pages/1485.html
PhoneGap 概要 Android SDKとHTMLを利用した開発 初期設定 雛形作成 作成方法
https://w.atwiki.jp/hotmilk005/pages/32.html
クラス変成 NSObject ↓ NSResponder ↓ NSView ビューのスクロールさせます NSTextView *textView=[[NSTextView alloc]init]; textView.frame=CGRectMake(0, 0, 200, 1000); textView.string=@"1\n2\n3\n4\n5\n6\n7\n8\n9"; NSScrollView *scrollView = [[NSScrollView alloc] init]; scrollView.frame=CGRectMake(100, 100, 100, 100); [scrollView setBorderType NSBezelBorder]; [scrollView setHasVerticalScroller YES]; [scrollView setHasHorizontalScroller YES]; [scrollView setDocumentView textView]; [self.window.contentView addSubview scrollView]; テーブルビューinスクロールビュー [[NSTableView]] *tcv=[[NSTableView alloc]initWithFrame CGRectMake(0, 0, 300, 100)]; NSTableColumn *coll_1=[[NSTableColumn alloc]initWithIdentifier @"coll_1"]; NSTableColumn *coll_2=[[NSTableColumn alloc]initWithIdentifier @"coll_2"]; [tcv addTableColumn coll_1]; [tcv addTableColumn coll_2]; tcv.delegate=self; tcv.dataSource=self; NSScrollView *scrollView = [[NSScrollView alloc] init]; scrollView.frame=CGRectMake(100, 100, 300, 100); [scrollView setBorderType NSBezelBorder]; [scrollView setHasVerticalScroller YES]; [scrollView setHasHorizontalScroller YES]; [scrollView setDocumentView tcv]; [self.window.contentView addSubview scrollView]; メソッド名 メソッドの効果 - (void)setBorderType (NSBorderType)borderType ボーダーの設定 - (void)setHasVerticalScroller (BOOL)flag 垂直スクロールの有無 - (void)setHasHorizontalScroller (BOOL)flag 水平スクロールの有無 - (void)setDocumentView (NSView *)aView スクロールビューにスクロールするビューを乗せる
https://w.atwiki.jp/wikiroid/pages/54.html
作者 Intuitit URL http //apps.intuitit.mobi/ Ver 0.8.0.9 言語 英語 Link アンドロイダー http //androider.jp/?p=1992 AndroLib http //jp.androlib.com/android.application.mobi-intuitit-android-launcher-xqED.aspx
https://w.atwiki.jp/parsecwiki/pages/23.html
※Urbano V4、Android9.0での設定方法です。他の端末、バージョンでは少し違うかもしれません。 １、BlutoothをONにする ２、設定を開き、接続済みの端末→新しいデバイスとペア設定をするを選択 ３、コントローラーをペアリングモードにする PS4コントローラーの場合はShareボタンとPSボタンを同時押し5秒程度 XBOXoneコントローラーは一度XBOXボタンを押して光らせた後、左上の黒いボタンを長押し２秒程度 ペアリングモードの際はランプが高速で点滅します ４、しばらくすると使用可能なデバイスにコントローラーが表示されるので選択して接続 ５、接続されている端末にコントローラーが表示されていたら接続完了です コントローラーのランプが点灯しているはず
https://w.atwiki.jp/matchmove/pages/71.html
3-D Review After SynthEyes has solved your scene, you’ll want to check out the paths in 3-D, and see what an inserted object looks like. SynthEyes offers several ways to do this traditional fixed 3-D views, including a Quad orthogonal isometric view, camera-view overlays, user-controlled 3-D perspective window, preview movies, and velocity vs time curves. Quad View If you are not already in Quad view, switch to it now on the toolbar . You will see the camera/object path and 3-D tracker locations in each view. You can zoom and pan around using the middle mouse button and scroll wheel. You can scrub or play the shot back in real-time (in sections, if there is insufficient RAM). See the View menu for playback rate settings. Camera View Overlay To see how an inserted object will look, switch to the 3-D control panel . Turn on the Create tool (magic wand). Select one of the built-in mesh types, such as Box or Pyramid. Click and drag in a viewport to drag out an object. Often, two drags will be required, to set first the position and breadth, then a second drag to set the height or overall scale. A good coordinate-system setup will make it easy to place objects. To adjust object size after creating it, switch to the scaling tool . Dragging in the viewport, or using the bottommost spinner, will adjust overall object size. Or, adjust one of the three spinners for each coordinate axis size. When you are tracking an object and wish to attach a test object onto it (horns onto a head, say), switch the coordinate system button on the 3-D Panel from to . Note the camera-view overlay is quick and dirty, not anti-aliased like the final render in your animation package will be (it has “jaggies”), so the overlay appears to have more jitter than it will then. You can sometimes get a better idea by zooming in on the shot and overlay as it plays back (use Pan-To-Follow). Shortly, we’ll show how to use the Perspective window to navigate around in 3-D, and even render an antialiased preview movie. Checking Tracker Coordinates If SynthEyes finds any trackers that are further than 1000 times the world size from the origin, it will not save them as “solved.” You can use the Script menu s Select By Type script to locate and select Unsolved trackers. You can change them to Zero-weighted to see where they might fall in 3-D, and prevent them from affecting future solves. Frequently these trackers should either distant horizon points that should be changed to Far, corrected, or deleted if they are on a moving object or the result of some image artifact. Such points can also arise when a tracker is visible for only a short time when the camera is not moving. The Clean up trackers dialog can do this automatically. Note the too-far-away test can cause trouble if you have a small world size setting but are using measured GPS coordinates. You should offset the scene towards the origin using the Shift Constraints script. You should also look for trackers that are behind the camera, which can occur on points that should be labeled Far, or when the tracking data is incorrect or insufficient for a meaningful answer. After repairing, deleting, or changing too-far-away or behind-camera trackers, you should use the Refine mode on the Solver panel to update the solution, or solve it from scratch. Eliminating such trackers will frequently provide major improvements in scene geometry. Checking Tracker Error Curves After solving, the tracker 3-D error channel will be available in the graph editor . It is important to understand the 3-D error it is the distance, in pixels, on each frame, between the tracker s 2-D position, and the position in the image of the solved 3-D tracker position. Let s work this through. The solver looks at the whole 2-D history of a tracker to arrive at a location such as X=3.2, Y=4.5, Z=0.1 for that tracker. On each frame, knowing the camera s position and field of view, we can predict where the tracker should be, if it really is at the calculated XYZ. That s the position at which the yellow X is displayed in the camera view after solving. The 3-D error is the distance between where the tracker actually is, and the yellow X where it should be. If the tracking is good, the distance is small, but if the tracking has a problem, the tracker is away from where it should be, and the 3-D error is larger. Obviously, given this definition, there s no 3-D error display until after the scene has been solved. You should check these error curves using the fundamentals described earlier in Pre-Solve Tracker Checking, but looking at the Error channel. Here we’ve used isolate mode to locate a rather large spike in the blue error curve of one of the trackers of a shot. This glitch was easy to pick out—so large the U and V velocities had to be moved out of the way to keep them clearly visible. The deglitch tool easily fixes it. You can look at the overall error for a tracker from the Coordinate System panel . This is easiest after setting the main menu s View/Sort by Error, unselecting all the trackers (control/command-D), then clicking the down arrow on your keyboard to sequence through the trackers from worst towards best. In addition to the curves in the graph editor, you can see the numeric error at the bottom of the tracker panel both the total error, and the error on the current frame. You can watch the current error update as you move the tracker, or set it to zero with the Exact button. For comparison, following is a tracker graph that has a fairly large error; it tracks a very low contrast feature with a faint moving highlight and changing geometry during its lifespan. It never has a very large peak error or velocity, but maintains a high error level during much of its lifespan, with some clearly visible trends indicating the systematic errors it represents. And finally, a decent tracker with a typical error level The vertical scale is the same in these last three graphs. (Note that in the 3rd one, the current time is to the left, before frame 160 or so, hence the blue arrow.) You can sort the trackers within the graph editor s Active Trackers node by changing Sort Alphabetic to Sort By Error . Do not blindly correct apparent tracking errors. A spike suggesting a tracking error might actually be due to a larger error on a different tracker that has grossly thrown off the camera position, so look around. Check for a Smooth Camera Path You should also check that the camera or object path is satisfactorily smooth, using the camera nodes in the graph editor. We’ve closed the Active Trackers node, and exposed the Camera Objects node and the Camera01 node within it. We’re looking at subset of the velocities of the camera the X, Y, and Z translation velocities. There s a spike around frame 215-220, to find it, expose the Active Trackers, select them all (control/command-A), and use Isolate mode around that range of frames. The result We’ve found the tracker that causes the spike, and can use the deglitch tool , or switch back to the tracker control panel and camera viewport, unlock the tracker, correct it, then re-lock it. Tip In the capture above, the selected tracker is not visible in the hierarchy view. You can see where it is in the scroll bar, though—it is located at the white spot inside the hierarchy view s scroll bar. Clicking at that spot on the scroll bar will pan the hierarchy view to show that selected tracker. If that is the last glitch to be fixed, switch to the Solve control panel , and re-solve the scene using Refine mode. You can also use the Finalize tool on the tracker control panel to smooth one or more trackers, though significant smoothing can cause sliding. If your trackers are very noisy, check whether film grain or compression artifacts are at fault, which can be addressed by image-preprocessor blur, verify that the interlace setting is correct, or see if you should fine-tune the trackers. Alternatively, you can fix glitches in the object path by using the deglitch tool directly on the camera or moving object s curves, because it works on any changeable channel. You can also move the object using the 3-D viewports and the tools on the 3-D control panel , by repositioning the object on the offending frame. Warning #1 If you fix the camera path, instead of the tracker data, then later re-solve the scene, corrections made to the camera path will be lost, and have to be repeated. It is always better to fix the cause of a problem, not the result. If you have worked on the trackers to reduce jitter, but still need a smoother path (after checking in your animation package), you can turn up the Filter Size control on the Solver panel. A filter size of 2 or 3 should make substantial reductions in jitter. After adjusting the control, switch to Refine mode and hit Go! again to apply the filtering. Warning #2 filtering the path this way increases the real error, and causes sliding. Remember that your objective is to produce a clean insert in the image, not produce an artificially smooth camera trajectory that works poorly.
https://w.atwiki.jp/droid/pages/34.html
* Google Sky Map（無料） https //market.android.com/details?id=com.google.android.stardroid さかなクン（無料） https //market.android.com/details?id=com.mobileroadie.app_1413
https://w.atwiki.jp/bemani2dp/pages/3860.html
GENRE TITLE ARTIST bpm notes CLEAR RATE J-POP And-RoiD Fujishiro feat.KNA 173 ? ?%(yyyy/mm/dd) コメント・攻略 名前 コメント
https://w.atwiki.jp/memosite/pages/79.html
20130301 最近のバージョンでは、NDK単体で作成可能らしい 20130302 Lock画面に文字はだせるっぽい。 20130303 Eclipseが起動しない。Error も吐かない。。。 java と javac はpath通ってる。 解凍失敗したかな？
https://w.atwiki.jp/zeratin7997/pages/19.html
評価 B- (S± A± B± C±) 良い所 スプレッドが狭い。(USD/JPYが大体0.4pips) Android版アプリのUIや操作性が良い。 MT4(自動売買)に対応している。 悪い所 10万通貨以上の取引を行う場合、スプレッドが結構広くなる。 スワップポイントが低い。 結局DD業者。最大のマイナスポイント。 総評 10万通貨以上の取引をしない場合は、特に欠点が見当たらない。 スワップポイント目当ての長期保有なら外為どっとコムに軍配が上がる。
https://w.atwiki.jp/cscd/pages/136.html
こんなことやってないで卒研やれ俺、って感じですが。 ProcessingをAndroid上で動かすことができます。ググるとその情報はいっぱいでてきて、みんなすんなり動いてるのだが（だいたい2009年時点くらい）、僕はWindows, Mac OS X, Linux(Ubuntu)と3つの環境で試してみても同じエラーが出てエミュレータが起動しない。それでようやく重い腰をあげてエラーメッセージをググったところ、 build.xml obsolete - help needed - Processing Forum が一番上に出てきた。で、この中に解決策として Visual Micro | How to fix android build.xml errors in processing 1.5＞2.0 beta が提示されていた。このとおりにやったらできたので報告しとく。どうもSDKの14とか新しいのだとだめらしいので、古いのを上書きするという手荒な感じ。あとこの記事によると、processingの2.0α4からはこのエラーはないらしい？ とりあえず環境が整ったので高エネルギー系の計算が出来る電卓をつくりたいな、と。山中電卓に対抗する。 2012.01.14(OK) 名前 コメント すべてのコメントを見る